-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: adding support for arbitrary field #2717
feat: adding support for arbitrary field #2717
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2717 +/- ##
==========================================
- Coverage 60.44% 60.43% -0.02%
==========================================
Files 563 563
Lines 75159 75159
==========================================
- Hits 45431 45419 -12
- Misses 26341 26349 +8
- Partials 3387 3391 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…RITORI/gno into feat/support-arbitrary-fields
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the tweak 🙏
I've left a few comments that should be addressed before we move forward
@hthieu1110 |
Signed-off-by: Norman Meier <norman@samourai.coop>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for applying the fixes 🙏
Related to this PR and Manfred's idea, this PR aims at adding possibility to add arbitrary field to profile.
I keep the same fields list defined in the struct, they would be served as "standard/base" fields and all other arbitrary fields are considered as "extra".
Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description